Web: a11y improvements + new properties - #3381

Could you PTAL at the failing A11yScrollTest?

Apolo (@ApoloApps) do the web tests pass for you locally?

Apolo (@ApoloApps) do the web tests pass for you locally?

nope, still investigating...

Oleksandr Karpovich (@eymar) okay seems to work locally and I have started the web tests in my fork's github actions and waiting for the results (CONFIRMED THEY PASS✅🥳). I do think all of it is fixed and I'm pretty confident.

• offsetLeft/offsetTop has to be used instead of style transforms since dom scrolling is not affected by the transforms
• hardcoding px values for tests was a bad idea, replaced it with a dynamic dom based approach. There was also some timeouts based on dom scrolling not finishing to pass to compose scroll, which didnt assert and caused timeouts. (these changes were merged following Fable 5 conversation)
  Another problem with tests may also stem from the fact that window must be on the front and not backgrounded since Chrome causes throttling in some promises (rAf and other timers). Does seem to reproduce on my machine Win11 Chrome, when window is behind intellij idea for example, my workaround: manually focusing window or applying these flags to karma test config file:

// Keep requestAnimationFrame & timers running when the Chrome window
                // is occluded or unfocused (frequent for local runs on Windows):
                 "--disable-backgrounding-occluded-windows",
                 "--disable-renderer-backgrounding",
                "--disable-background-timer-throttling",
                 "--disable-features=CalculateNativeWinOcclusion"